Programme Lead
Programme Leads create and edit Forms from within the project Dashboard. It is the Programme Lead's responsibility to:
- Create projects, assign access permissions and make the project available to users.
- Create and maintain data entry Forms and Editors.
A data entry Form can be designed to:
Users enter data in a Form which creates or updates one record in an EMu module as the Form is saved: there is a one to one relationship between the data entered in the Form and a record in an EMu module.
The following screenshot shows the design of a data entry Form to capture details of a Person
Party. The Form comprises a single section with four fields (only the first is shown) and a search section:
When accessed by a user, the Form will display as:
When details are entered and the Form is saved, a record is created in the Parties module.
The search option can be used to locate a record in the Parties module, which can be edited and saved.
Some features of this Form:
# |
Feature |
---|---|
1 |
Clicking the information icon will display a pop-up with details about the purpose of the Form: |
2 |
This field has been configured as mandatory. The Form cannot be saved unless a value is entered in the field. |
3 |
A drop list of available values for the field. |
4 |
Searches the Parties module for a record and displays its values in the Form, where they can be edited and saved back to the Parties module. |
Rather than creating or editing a single record when a Form is saved, the Form data can be processed by a script to manipulate it in any number of ways.
A typical use of a Processing Script is bulk creation of records.
Note: Processing scripts are written in perl, typically by Axiell developers. A number of scripts are available and can be provided on request; additional scripts can be written to meet a customer's requirements. Please contact Axiell Support to discuss.
Each project has a directory on the IMu server located beneath the forms
directory. Processing scripts for a project are saved to this directory.
It is not necessary to enter the name of the script in the Processing script field if there is only one script assigned to the Form and the script is named using the Form's Identifier with a .pl
suffix (this becomes the default script), e.g.:
imaging.pl
If there is more than one processing script available (and you do not wish to use the default script), enter the name of the script to use in the Processing script field:
Creating a project and making it available to users involves three steps:
- Name the project in the EMu Registry.
- Define user access in the EMu Registry:
- Assign permissions to users to determine what elements (Forms, Editors, Statistics) of the project they have access to.
Note: As with assigning permissions in EMu, it is good practice to assign permissions to a group and to make users members of the group. Permissions can be assigned to users, of course, and these will take precedence over group level permissions. See the EMu Help for details about the order in which Registry entries are assigned.
- Define a user's role in a project.
- Define which projects the user has access to.
See Axiell Sapphire Registry entries for details.
- Assign permissions to users to determine what elements (Forms, Editors, Statistics) of the project they have access to.
- Create Forms and Editors, and Statistical graphs.